-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(web): fixes error on tab, enter when only a single input element is on the page #11470
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
@@ -38,7 +38,7 @@ export default class DefaultBrowserRules extends DefaultRules { | |||
const contextManager = this.contextManager; | |||
const activeElement = contextManager.activeTarget?.getElement(); | |||
const nextElement = contextManager.page.findNeighboringInput(activeElement, back); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The function can explicitly return null
, yet we weren't null-guarding on the result.
…is on the page Cherry-pick-of: #11470
Changes in this pull request will be available for download in Keyman version 18.0.45-alpha |
3 similar comments
Changes in this pull request will be available for download in Keyman version 18.0.45-alpha |
Changes in this pull request will be available for download in Keyman version 18.0.45-alpha |
Changes in this pull request will be available for download in Keyman version 18.0.45-alpha |
Resolves an error reported by a user from KeymanWeb 16.0.
It was reported to occur whenever a page contained only one valid context-hosting element - an
<input>
- and when the user pressed the ENTER key on the touch OSK.@keymanapp-test-bot skip